David Karich

Thanks @ryan works perfectly and so easy.

Hi @ryan, as I am actively working on updates, I am now at the point where I would like to use the versions. Now I have exactly the problem that the automatically by my module added field "phits" is versioned. But it should not. I know I can explicitly select fields during the restore and could omit this field, but this is not practicable for the users and they forget about it. And suddenly all the statistics are gone. Unfortunately, I also can't find any info on whether I can hook into "$pagesVersions->restorePageVersion" or "$pagesVersions->savePageVersion" to always skip the "phits" field. Do you have any other idea how I can tell the module that it should not be versionable? The field is just a very simple fieldtype: https://github.com/flipzoom/PageHitCounter/blob/master/FieldtypePageHitCounter.module Thank you and best regards

Hi @FireWire First of all, thank you for the module and all the work you have put into it! I just wanted to test the module in a real world project, but quickly realised that certain terms are always translated incorrectly by Deepl. In the web version this is easy to solve with the personal glossary. Is there also a way to create a glossary here, or to tell the API in some way to use my glossary from my account?

Unfortunately, that's how I understood it and I didn't understand it. Actually, all the real gamechanger proposals were rejected, especially the ones that so many people have been asking for years. At its core, PW is obviously tied to what Ryan needs it for, not the community.

Yes, exactly. I am also aware that there is still some time left, but I don't want to delay the situation until the last minute, because many customers have and send via Office365. ?

I think the most talked about feature is an asset manager. The drilling down of file and imagefields so that you can choose assets from a global library that have already been uploaded somewhere, instead of having to upload assets multiple times. Actually, the approach using references is the best I've come across so far. The data remains where it was originally uploaded, but is only referenced in a file/image field on another page.

Hey guys, Microsoft is deactivating SMTP Basic Authentication at the end of the year. https://learn.microsoft.com/en-gb/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online Has anyone already found a solution to get Office365 working with OAuth 2.0? @ryan would it be possible to adapt your "WireMailGmail" module? Or maybe someone is knowledgeable enough to design a general OAuth wireMail module? ?

Hi @Leftfield, the detection is done via a simple RegEx in a match group. You can add the string "Screaming Frog SEO Spider" with spaces to the list. But without a pipe at the end. go-http-client|googlebot|bingbot|link|googlebot-image|yandexbot|semrushBot|ahrefsBot|zoominfobot|applebot|seznambot|yak-linkfluence|barkrowler|blexbot|yandeximages|cfnetwork|linkedinbot|feed|dalvik|validator|baiduspider|2345Explorer|survey|surdotlybot|Screaming Frog SEO Spider

@ryan I'm really looking forward to testing it! Awesome. One question in advance: are there ways to exclude Fieldtypes? Example, my module PageHitCounter. The number of hits should of course not be overwritten by another version. I haven't tested it yet, but is it the case that if a Fieldtype doesn't have a version interface implemented, it won't be versioned?

Hey @ryan, I'm so excited about the feature. The two big things I think ProcessWire is missing are versioning and a lack of global asset management. ProDrafts was a good approach so far, but had limitations. Can you perhaps briefly explain how the versioning module works? ProDraft had the approach that everything I save is saved in a draft until I publish. Is this also the approach here, that every time I save a page a new version of the last state before saving is created or do I have to create a new version myself beforehand, in which I work, revise a draft and then "restore" it when I'm done as a form of "fake" publishing?

No, this is not possible. As described in the cons, the hits are only summed up and no historical data is collected. The module has no claim to be a statistics module, only a small helper for a quick overview of accesses and interest-based sorting. Please ask @bernhard, he once wrote an extension as a module, which should extend my module with these functions.

Hey @kongondo, is there actually anything new to see here? ?

Wow. Looks absolutely incredible. ? Really gives you a feel of an asset library. Great work. Looks intuitive too. Can't wait to test it out. ? Two questions: how should uploads happen? Can I just upload assets via DND in a folder or is the "New" button meant for uploads? If so, I would give it a different name, e.g. "Upload Media". Second question: does the search always refer to the entire library or only to the currently selected folder? Can I change the search behaviour in an advanced mode?

Hey @Robin S, thanks for this incredibly useful module. Since PW is now more oriented towards TinyMCE and I am already adapting new projects as well, the question is whether you have plans to port this module for TinyMCE as well?

@kongondo And because it is so much fun to think about the new MM and which requirements are more difficult to implement so far, I have another feature request. ? I have a few multi-language websites that keep running into the problem that different images have to be displayed depending on the language, e.g. because there is text on the images. Currently, I can only solve this in a complicated way using the PW-internal option with image tags. Personally, I find this a design workflow break in the whole PW concept, because the rest works wonderfully with the LangTabs modules. Perhaps also a feature request to @ryan at this point. ? My wish here would be to map the MM-InputfieldImage in the same way as multi-lang text fields. So with a simple language switch, select another item from the library.